Skip to content

[Project Darkstar] ROSAENG-61595: Remediate CVE-2026-15308 in managed-scripts#277

Draft
kseiter-rh wants to merge 1 commit into
openshift:mainfrom
kseiter-rh:cve-fix/managed-scripts-darkstar-2026-07-16
Draft

[Project Darkstar] ROSAENG-61595: Remediate CVE-2026-15308 in managed-scripts#277
kseiter-rh wants to merge 1 commit into
openshift:mainfrom
kseiter-rh:cve-fix/managed-scripts-darkstar-2026-07-16

Conversation

@kseiter-rh

@kseiter-rh kseiter-rh commented Jul 16, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

Project Darkstar — Automated CVE Remediation

This PR was generated by Project Darkstar, an automated CVE remediation tool.
For questions or concerns, contact Kevin Seiter (ROSA Trust Engineering).

Summary

  • Fixes CVE-2026-15308 (Important, CVSS 7.5) — Python CPU DoS in html.parser
  • Updates UBI8 base image from 8.10-1779891713 to 8.10-1781720109 in both Dockerfile stages
  • Aligns Dockerfile with the tag already used in .tekton/pr-check-pipeline.yaml

CVE Details

  • CVE: CVE-2026-15308
  • Severity: Important (CVSS 7.5)
  • CWE: CWE-835 (Uncontrolled Loop / Infinite Loop)
  • Description: Python's html.parser.HTMLParser allows CPU denial-of-service via repeated unterminated markup declarations in uncontrolled input.
  • Fix: Red Hat backported the fix to python3.11 (RHSA-2026:38017/38018). Updating the UBI8 base image tag triggers a rebuild that pulls the patched python3.11 RPM from Red Hat's online repos.

CVEs Analyzed But Not Auto-Fixed (require action outside this repo)

CVE Severity Component Reason
CVE-2026-44740 Important (7.5) go-billy v5 Transitive dep in hypershift — fix in openshift/hypershift go.mod
CVE-2026-53492 Important (8.2) containerd CRI plugin Runtime-level — update containerd at cluster/node level
CVE-2026-53488 Important (8.8) containerd CRI plugin Runtime-level — update containerd at cluster/node level
CVE-2026-42306 Important (7.2) Moby/Docker Engine Runtime-level — update Docker Engine to 29.5.1

Changes

  • Dockerfile: Updated both FROM lines from ubi8/ubi:8.10-1779891713 to ubi8/ubi:8.10-1781720109

Verification

  • CI/CD pipeline (make build) passes with new base image
  • No regressions in existing script validation
  • New base image tag is on the same 8.10 major.minor stream

References

Project Darkstar — Automated CVE Remediation | Contact: Kevin Seiter (ROSA Trust Engineering)

@kseiter-rh @claude
fix(security): [Project Darkstar] remediate CVE-2026-15308 — update u…
47b5f72 
…bi8/ubi to 8.10-1781720109

Addresses CVE-2026-15308 (Important, CVSS 7.5).
Python's html.parser allows CPU DoS via repeated unterminated markup
declarations. Updated UBI8 base image to 8.10-1781720109 in both build
and final stages; rebuild will pull the patched python3.11 RPM from
Red Hat's UBI8 content repos.

Ref: ROSAENG-61595
Project Darkstar — automated CVE remediation (contact: Kevin Seiter)

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot

openshift-ci-robot commented Jul 16, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@kseiter-rh: This pull request references ROSAENG-61595 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the vulnerability to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Project Darkstar — Automated CVE Remediation

This PR was generated by Project Darkstar, an automated CVE remediation tool.
For questions or concerns, contact Kevin Seiter (ROSA Trust Engineering).

Summary

  • Fixes CVE-2026-15308 (Important, CVSS 7.5) — Python CPU DoS in html.parser
  • Updates UBI8 base image from 8.10-1779891713 to 8.10-1781720109 in both Dockerfile stages
  • Aligns Dockerfile with the tag already used in .tekton/pr-check-pipeline.yaml

CVE Details

  • CVE: CVE-2026-15308
  • Severity: Important (CVSS 7.5)
  • CWE: CWE-835 (Uncontrolled Loop / Infinite Loop)
  • Description: Python's html.parser.HTMLParser allows CPU denial-of-service via repeated unterminated markup declarations in uncontrolled input.
  • Fix: Red Hat backported the fix to python3.11 (RHSA-2026:38017/38018). Updating the UBI8 base image tag triggers a rebuild that pulls the patched python3.11 RPM from Red Hat's online repos.

CVEs Analyzed But Not Auto-Fixed (require action outside this repo)

CVE Severity Component Reason
CVE-2026-44740 Important (7.5) go-billy v5 Transitive dep in hypershift — fix in openshift/hypershift go.mod
CVE-2026-53492 Important (8.2) containerd CRI plugin Runtime-level — update containerd at cluster/node level
CVE-2026-53488 Important (8.8) containerd CRI plugin Runtime-level — update containerd at cluster/node level
CVE-2026-42306 Important (7.2) Moby/Docker Engine Runtime-level — update Docker Engine to 29.5.1

Changes

  • Dockerfile: Updated both FROM lines from ubi8/ubi:8.10-1779891713 to ubi8/ubi:8.10-1781720109

Verification

  • CI/CD pipeline (make build) passes with new base image
  • No regressions in existing script validation
  • New base image tag is on the same 8.10 major.minor stream

References

Project Darkstar — Automated CVE Remediation | Contact: Kevin Seiter (ROSA Trust Engineering)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 16, 2026
@openshift-ci

openshift-ci Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 16, 2026
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kseiter-rh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 83fd6d20-fc74-4d71-a632-68e848d5d551

📥 Commits

Reviewing files that changed from the base of the PR and between a90e7f7 and 47b5f72.

📒 Files selected for processing (1)
  • Dockerfile
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kseiter-rh
Once this PR has been reviewed and has the lgtm label, please assign matesaary for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kseiter-rh @openshift-ci-robot